Skip to content

Phase 3: SHA512 integrity check and closing the final FIPS requirements gaps#10281

Open
kaleb-himes wants to merge 1 commit into
wolfSSL:masterfrom
kaleb-himes:PQ-FS-2026-Part3-SecurityReview
Open

Phase 3: SHA512 integrity check and closing the final FIPS requirements gaps#10281
kaleb-himes wants to merge 1 commit into
wolfSSL:masterfrom
kaleb-himes:PQ-FS-2026-Part3-SecurityReview

Conversation

@kaleb-himes

@kaleb-himes kaleb-himes commented Apr 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Description

This PR is 6 major items as follows:

  1. What got missed from the FIPS standards - fix
  2. Add a new CAST benchmark app so one can see how long the power up tests take
  3. Classic DH is leaving the FIPS module in it's entirety (No more FFDHE)
  4. Get AESNI working in 32-bit linux kernel space
  5. Get ARM 32 (Neon) working in 32-bit linux kernel space
  6. Get ARM 64 (ARMv8) working in 64-bit linux kernel space (edited)

Testing

<head></head>
OE | Arch / Space | C1 | C2 | C3
-- | -- | -- | -- | --
U3 | x86_64 Intel · user | ✅ | ✅ | ✅
U5 | x86_64 AMD · user | ✅ | ✅ | ✅
U1 | i386 Intel · user | ✅ | ✅ | ✅ AES-NI
U7 | ARM64 · user | — | — | ✅ armasm
U6 | ARM32 · user | — | — | ✅ armasm
U4 | x86_64 Windows · MSVC | ✅ | ✅ | ✅ AES-NI
U2 | i386 Windows · MSVC | ✅ | ✅ | ⚪ NA
K1 | i386 · kernel | ✅ | ✅ | ✅ AES-NI
K2 | x86_64 Intel · kernel | ✅ | ✅ | ✅
K3 | x86_64 AMD · kernel | ✅ | ✅ | ✅
K4 | ARM32 · kernel | ✅ | ✅ | ✅ armasm
K5 | ARM64 · kernel | ✅ | ✅ | ✅ armasm

Checklist

  • added tests
  • updated/added doxygen
  • updated appropriate READMEs
  • Updated manual and documentation

@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch 3 times, most recently from 8923ea5 to 9af5352 Compare April 22, 2026 22:51
@github-actions

github-actions Bot commented Apr 22, 2026 •
edited
Loading

Copy link
Copy Markdown

MemBrowse Memory Report

gcc-arm-cortex-m3

  • FLASH: .text +32 B (+0.0%, 122,557 B / 262,144 B, total: 47% used)

gcc-arm-cortex-m4-baremetal

  • FLASH: .text +64 B (+0.1%, 66,891 B / 262,144 B, total: 26% used)

gcc-arm-cortex-m4-dtls13

  • FLASH: .text +64 B (+0.0%, 181,016 B / 1,048,576 B, total: 17% used)

gcc-arm-cortex-m4-openssl-compat

  • FLASH: .text +64 B (+0.0%, 771,620 B / 1,048,576 B, total: 74% used)

gcc-arm-cortex-m4-pkcs7

  • FLASH: .text +64 B (+0.0%, 213,050 B / 262,144 B, total: 81% used)

gcc-arm-cortex-m4-pq

  • FLASH: .text +128 B (+0.0%, 279,928 B / 1,048,576 B, total: 27% used)

gcc-arm-cortex-m4-tls12

  • FLASH: .text +64 B (+0.1%, 123,341 B / 262,144 B, total: 47% used)

gcc-arm-cortex-m7

  • FLASH: .text +64 B (+0.0%, 200,654 B / 262,144 B, total: 77% used)

gcc-arm-cortex-m7-pq

  • FLASH: .text +128 B (+0.0%, 280,504 B / 1,048,576 B, total: 27% used)

linuxkm-pie

  • Data: __patchable_function_entries +16 B (+0.1%, 25,984 B)

linuxkm-standard

@kaleb-himes kaleb-himes changed the title Pq fs 2026 part3 security review Phase 3: SHA512 integrity check and closing the final FIPS requirements gaps Apr 23, 2026
@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch 3 times, most recently from a43af0f to 7c0c87a Compare April 29, 2026 14:06
Frauschi
Frauschi previously requested changes Apr 30, 2026
View reviewed changes

@Frauschi Frauschi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only found one small possible memory usage optimization. Otherwise LGTM

Comment thread wolfcrypt/src/wc_slhdsa.c Outdated
@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch 9 times, most recently from e3f56b8 to 29c714f Compare May 1, 2026 20:03
@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch 4 times, most recently from b883766 to a6681e2 Compare May 27, 2026 22:14
@kaleb-himes

kaleb-himes commented May 28, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

retest this please.

@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch from a6681e2 to 588e7a0 Compare June 8, 2026 15:46
@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch 3 times, most recently from 57ef11a to 064812c Compare June 22, 2026 22:24
@kaleb-himes
kaleb-himes requested a review from Frauschi June 22, 2026 22:25
@kaleb-himes
kaleb-himes dismissed Frauschi’s stale review June 22, 2026 22:26

Fixed noted items, dismissing review for a re-review.

@kaleb-himes
kaleb-himes marked this pull request as ready for review June 25, 2026 20:25
@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown

retest this please

@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch 6 times, most recently from 6a9d5f1 to be03cda Compare July 2, 2026 15:57
@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch 8 times, most recently from 04dea06 to 80e850a Compare July 11, 2026 21:42
@jackctj117
jackctj117 self-requested a review July 15, 2026 16:54
@kaleb-himes

kaleb-himes commented Jul 16, 2026 •
edited by jackctj117
Loading

Copy link
Copy Markdown
Contributor Author

retest this please.

@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch 10 times, most recently from 48bd784 to 86af2ea Compare July 20, 2026 16:39
@kaleb-himes
kaleb-himes force-pushed the PQ-FS-2026-Part3-SecurityReview branch from 86af2ea to 3bc5760 Compare July 20, 2026 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Frauschi Frauschi Awaiting requested review from Frauschi
@douzzer douzzer Awaiting requested review from douzzer
@SparkiDev SparkiDev Awaiting requested review from SparkiDev
@jackctj117 jackctj117 Awaiting requested review from jackctj117

At least 1 approving review is required to merge this pull request.

Assignees

@kaleb-himes kaleb-himes

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@kaleb-himes @Frauschi